deps: add 3-day release-age cooldown to shared Renovate preset (first-party exempt)#31
Merged
Merged
Conversation
Harden the shared Renovate baseline against supply-chain risk. The preset auto-merges a lot (patch, digest, npm devDep minor, and ~8 grouped families), so a freshly-published compromised or broken version could auto-merge within minutes. config:best-practices does not set a cooldown on its own. - minimumReleaseAge: "3 days" + internalChecksFilter: "strict" so a bad upstream release has time to be yanked before it can auto-merge. - First-party exemption (ANcpLua.* + Qyl.*, nuget): minimumReleaseAge "0" so our own releases still propagate across the fleet immediately. Validated with renovate-config-validator: "Config validated successfully". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a supply-chain cooldown to the shared Renovate baseline (
default.json), which every ANcpLua/Qyl repo extends viagithub>ANcpLua/github-settings-automation.Plus a first-party exemption packageRule so our own packages skip the wait:
{ "matchDatasources": ["nuget"], "matchPackageNames": ["/^ANcpLua\\./", "/^Qyl\\./"], "minimumReleaseAge": "0" }Why
The preset auto-merges aggressively — patch, pin/digest, lockfile, npm devDep minor, and ~8 grouped families (roslyn, testing, otel, ms-extensions, ai-clients, meziantou, openapi, ancplua-sdk).
config:best-practicesdoes not add a release-age cooldown, so a freshly-published compromised or broken third-party version can auto-merge within minutes of release. A 3-day cooldown gives a bad upstream release time to be yanked/patched before it can land.internalChecksFilter: "strict"holds the PR until the age gate passes.First-party
ANcpLua.*/Qyl.*are exempt (minimumReleaseAge: "0") because we publish them and want cross-repo propagation to stay immediate.Scope
One-line change to the fleet's single source of truth → hardens every repo that extends this preset at once.
Verification
renovate-config-validator default.json→ "Config validated successfully"🤖 Generated with Claude Code